DicomObjects.NET.V8
In This Topic
    Version 8 Release Notes
    In This Topic

    This new version of DicomObjects.NET consolidates numerous incremental changes and cleans up some of the unused remnants, as well as adding significant new features, the main one being the 2D and 3D GPU rendering.   The main changes are:

     2D/3D GPU rendering using DirectX (HLSL)

    The big advancement in this version is the GPU powered 2D and 3D rendering of images, which not only makes it a more stable option but also has a massive performance improvement with very impressive test results. Few fundamental changes to the rendering process are:

    • 3D images now have a single class, and hence it is possible to move between the types (MPR, Slab, MIP & VR) by changing the Mode property, without remaking the object.
    • A DicomVolume object can be used to make multiple 3D image objects, improving memory efficiency and saving CPU cycles.
     DICOM Fusion Image
    This is a totally new feature which can be utilised by using the DicomImageFusion class. It allows spatial transformations, which are passed on simultaneously to all the images in the collection.
     Video support using FFmpeg

    Starting with version 8 we have added video support with the help of FFmpeg, a well established video Codec, for handling all sorts of popular video formats. This allows importing of supported video formats, embedding them into DICOM and exporting them using the appropriate transfer syntax.

    FFmpeg is licensed under the GNU Lesser Public license(LGPL). We comply with the rules as stated in FFmpeg's licensing terms (https://www.ffmpeg.org/legal.html) for using this open-source Codec in our product and would urge our users to be aware of the legal responsibilities of using it.  For development status on this feature please check our webpage http://www.medicalconnections.co.uk/kb/Video_support_with_FFmpeg

     DicomLabel update
    There is a single major update in this new version as a result of our effort to have a consistent API for DicomLabel handling. We have fully documented the changes in our article.

    There have been many internal code changes that are related to code normalization, efficiency and readability and some of them affect deep rooted routines like handling sequences, writing to disk, network transmission, etc. Most of these don't directly affect our API but some changes were unavoidable. If you have any problems with this version please contact us our Support Team.